[API BREAK] Fix ECDSA message hashes to 32 bytes #150
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Good. I was thinking of at least clarifying the description that the message must be a hash. Fixing the length makes it slightly less foot-gunny. I'll review/test. |
|
ACK. |
sipa
added a commit
that referenced
this pull request
Dec 11, 2014
cf7b2b4 Fix ECDSA message hashes to 32 bytes (Pieter Wuille)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The message is assumed to be already hashed anyway, and it already can't be more than 32 bytes. Fixing it to a single size simplifies the code and the API.